-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
radxa-zero3 maintenance #8794
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
radxa-zero3 maintenance #8794
Conversation
WalkthroughThe pull request updates Radxa Zero3 board configuration by renaming and rewriting the mainline U-Boot handler function from Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes The changes involve two different files with relatively straightforward logic modifications. While heterogeneous in nature (branch control flow inversion vs. kernel version threshold adjustment), each change is simple and focused without extensive structural reorganization or dense logic patterns. Possibly related PRs
Suggested labels
Suggested reviewers
Pre-merge checks and finishing touches❌ Failed checks (1 warning, 1 inconclusive)
✅ Passed checks (1 passed)
✨ Finishing touches
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 0
🧹 Nitpick comments (1)
config/boards/radxa-zero3.csc (1)
59-61: LGTM: Cleaner logic and accurate function naming.The function rename and logic inversion improve code clarity. The new implementation achieves the same result (enabling mainline U-Boot for current/edge branches while keeping vendor on vendor U-Boot) but with simpler, more maintainable code. The inverted condition
[[ "${BRANCH}" == "vendor" ]]is easier to understand than the double-negative pattern it replaces.The new approach is also more general—any future non-vendor branches will automatically use mainline U-Boot without code changes.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
Disabled knowledge base sources:
- Jira integration is disabled by default for public repositories
You can enable these sources in your CodeRabbit configuration.
📒 Files selected for processing (2)
config/boards/radxa-zero3.csc(2 hunks)extensions/radxa-aic8800.sh(1 hunks)
🧰 Additional context used
🧠 Learnings (1)
📚 Learning: 2025-09-14T06:32:29.806Z
Learnt from: amazingfate
PR: armbian/build#8619
File: config/sources/families/rockchip.conf:222-230
Timestamp: 2025-09-14T06:32:29.806Z
Learning: In the Armbian build system, the write_uboot_platform() function implementations follow different patterns across Rockchip family files. The newer standard (used in rockchip64_common.inc and rk3506) includes 'status=none' parameter in dd commands, while older implementations (rk3288, rk322x) use an older pattern without this parameter. The rk3506 implementation correctly follows the current Rockchip family standard.
Applied to files:
config/boards/radxa-zero3.csc
🧬 Code graph analysis (2)
extensions/radxa-aic8800.sh (2)
extensions/v4l2loopback-dkms.sh (1)
post_install_kernel_debs__build_v4l2loopback_dkms_kernel_module(15-25)extensions/bcmdhd.sh (1)
post_install_kernel_debs__install_bcmdhd_dkms_package(11-47)
config/boards/radxa-zero3.csc (1)
config/sources/vendors/mekotronics/mekotronics-rk3588.hooks.sh (2)
post_family_config__meko_use_mainline_uboot(22-42)post_family_config__vendor_uboot_mekotronics(8-16)
🔇 Additional comments (2)
extensions/radxa-aic8800.sh (1)
13-16: Kernel version threshold adjustment looks correct.The change from
ge 6.18toge 6.19appropriately enables DKMS installation for Linux 6.18 kernels, aligning with the PR objective. The implementation follows the same pattern used in other DKMS extensions.However, note that Wi-Fi testing on the 3W variant (which uses this AIC8800 extension) was not performed per the PR description. Please verify Wi-Fi functionality on 6.18 kernels when hardware becomes available, or document this limitation if the 3W variant is commonly used.
config/boards/radxa-zero3.csc (1)
66-66: U-Boot version bump to stable is confirmed and ready.The update from
v2025.10-rc2tov2025.10is valid—the tag exists in the upstream repository—and the PR reports successful build and boot testing.
|
https://paste.armbian.com/acidafenox |
|
✅ This PR has been reviewed and approved — all set for merge! |
@EvilOlaf That could be work-around'ed: function post_family_config_branch_vendor__zero3_different_dtb_for_vendor() {
declare -g BOOT_FDT_FILE="rockchip/rk3566-radxa-zero3.dtb"
display_alert "$BOARD" "Using ${BOOT_FDT_FILE} for ${BRANCH}" "warn"
} |
|
Interesting, I'll try that tomorrow if I find some time. |
Description
Note: Tried to get rid of vendor uboot altogether but board naming differs, therefore uboot fails to find fdt file.
How Has This Been Tested?
Checklist: